Configuring Purchase Request Assumptions and Drivers

In Axiom Capital Tracking, each file group contains an associated driver file with configuration settings and assumptions referenced by all of the other files associated with that file group. Along with its other functions, the driver file allows you, as the administrator, to decide which sections to include or exclude from plan files and enter many of the values that display as pre-populated in plan files and reports.

The configuration settings in the driver files can affect the structure of plan files and reports by allowing you to show/hide sections of sheets, columns, and/or rows. Assumptions are used in calculations throughout the entire capital tracking process. Examples of assumptions include:

Volume growth rates
Inflation rates
Labor merit increases and benefits percentages
Reimbursement percentages

You access and update Axiom Capital Tracking drivers using the Purchase Request Drivers utility. You can also access this utility directly from the Axiom Capital Tracking web home screen. The drivers are grouped into two main driver file types: Configuration and Retrospective. These driver file types display at the top of the utility as tabs. To update the driver in a particular file, click the tab drop-down, and select the driver to update.

The following table describes each driver file and the drivers associated with it:

Driver File	Description	Drivers
Configuration	Includes general system settings and configuration selections, such as enabling system processes, custom fields for purchase request header inputs, and custom fields for purchase request line item inputs.	General Setup Purchase Request Header - Project Fields Purchase Request Header Fields Purchase Request Line Item Fields Purchase Request Header Picklists Purchase Request Line Item Picklists Field Name Tables
Retrospective	Includes questions related to capturing detailed inputs regarding retrospective project analysis.	Retro Comprehensive Updates Retro Status Updates

NOTE: Depending on a user's security profile settings, certain parts of a driver file may be protected.

IMPORTANT: Any change to the configuration settings and assumptions in driver files can affect the structure and contents of any number of related plan files.